Visual Basic (Declaration) | |
---|---|
Overloads Public Sub WriteTransformMarker( _ ByVal id As Integer, _ ByVal data() As Byte, _ ByVal dataOffset As Integer, _ ByVal dataLength As Integer _ ) |
Visual Basic (Usage) | Copy Code |
---|---|
|
C# | |
---|---|
public void WriteTransformMarker( int id, byte[] data, int dataOffset, int dataLength ) |
Managed Extensions for C++ | |
---|---|
public: void WriteTransformMarker( int id, byte[] data, int dataOffset, int dataLength ) |
C++/CLI | |
---|---|
public: void WriteTransformMarker( int id, array<byte> data, int dataOffset, int dataLength ) |
Parameters
You should use this method to write a certain marker data into the file.
This method can be called only from within the CodecsTransformMarkerCallback passed to the Transform method.
The transform mechanism is as follows:
You call Transform. Transform will call the CodecsTransformMarkerCallback callback passed to it for every marker contained in the source file. In the callback, you can replace markers, insert markers or allow Leadtools to do the default processing (recommended). You can override the default action for a marker by returning one of the following values from the transform callback: CodecsTransformMarkerAction.Default: Let Leadtools perform the default action on the marker. This means the marker might (or might not) be transformed and will be written to the destination file. CodecsTransformMarkerAction.Ignore: This marker will be ignored (this is useful for stripping unwanted markers). You should also use this if you want to do your own transformation and write the marker yourself by calling WriteTransformMarker. CodecsTransformMarkerAction.Abort: Abort the process. This will cause Transform to throw a 'user-abort' exception.
Note: You can also use WriteTransformMarker to insert your own markers. The marker will be inserted before the current marker. You can call WriteTransformMarker as many times as you wish. Every call to WriteTransformMarker will insert a new marker.
Warning: Incorrect handling of the markers will generate corrupt files! Since some markers contain important information about the image (image width, height, compression method, colorspace, etc), you should use caution when working with markers.
Target Platforms: Microsoft .NET Framework 2.0, Windows 98, Windows NT 4.0, Windows Millennium Edition, Windows 2000, Windows XP Home Edition, Windows XP Professional, Windows Server 2003 family